Exploring the influences on requirements engineering during global software development

Through an interpretive study of global virtual teams, this research has explored the influences on the requirements engineering processes during global software development. Complex layers of explicit and implicit elements in the project environment, including systems methodology, project steering, management commitment and cultural differences, were found to influence these processes.

Exploring the sociotechnical systems perspectives in global software development

Global software development teams expressed dissatisfaction with their structures. Job satisfaction was reduced by the inefficiencies of communication technologies and from the functional structures imposed by the management. This led to a reduced contextual understanding of projects which could be improved if employees were to participate in the work designs.

Global software development : the next RE frontier?

Requirements Engineers face an emerging set of challenges, which compound the traditional Requirements Engineering (RE) challenges (stakeholder identification, domain expertise, communication, analytic skills, problem solving, ...) that have arguably still not been fully addressed. This is the challenge of RE in the world of global software development, with requirements teams working in virtual mode (possibly on different continents), with the software having to operate in multiple contexts, addressing the needs of different cultures and legal jurisdictions, and having to build sales in different marketplaces. Further the need arises to specify software that is progressively enhanced through regular releases, rather than the “green field” specification of products.

This theoretical paper introduces these challenges, and presents an initial selection of theoretical models, drawn from many and varied source disciplines, which might be employed to gain insight into various features of RE in support of global software development. To illustrate the potential relevance of this selection of models, a longitudinal case study with a recently identified software developer, to follow the specification and subsequent roll-out of a future release of a software product for sale globally, is introduced. Features of the situation faced by that organisation are highlighted, to illustrate the potential relevance of the diverse models that have been identified.

Requirements engineering during global software development : some impediments to the requirements engineering process : a case study

Requirements engineering is not straightforward for any software development team. Developing software when team members are located in widely distributed geographic locations poses many challenges for developers, particularly during the requirements engineering phase. This paper reports on a case study concerning a large software development project that was completed in just seven months between users located in the UK and software developers from an international software house based in New Zealand. The case indicates that while “true” global requirements engineering may be desirable in achieving economy of resources, a “hybrid” structure of requirements engineering processes is more realistic so that lasting relationships with clients may be formed, and requirements engineering activities achieved. The main impediment to the process of requirements engineering during global software development, as recounted by the team members in this case, is communication. Communication issues may be further described in terms of four categories: distribution of the clients and the development team, distribution of the development team, cultural differences between the clients and the development team and cultural differences among the development team.

Analysing audio-recorded data : using computer software applications

Conventional methods of qualitative data analysis require transcription of audio-recorded data prior to conduct of the coding and analysis process. In this paper Alison Hutchinson describes and illustrates an innovative method of data analysis that comprises the use of audio-editing software to save selected audio bytes from digital audio recordings of meetings. The use of a database to code and manage the linked audio files and generate detailed and summary reports, including reporting of code frequencies according to participant code and/or meeting, is also highlighted. The advantage of using this approach in the analysis of audio-recorded data is that the process may be undertaken in the medium in which the data were collected. Though time-consuming, this process negates the need for expensive and time intensive transcription of recorded data.

Critical success factors for the requirements engineering process, with reference to quality management of information systems development

Preliminary research into the critical factors associated with software development/implementation identified three dimensions for successful implementation based on alignment of the requirements engineering process with business needs, change management process and quality of the implementation process. Research results demonstrate the link between the conceptual model for process quality and the process management attributes determined during the research.

A taxonomy of dependencies in agile software development

Dependencies in a software project can contribute to unsatisfactory progress if they constrain or block the flow of work. Various studies highlight the importance of dependencies in the organisation of work; however dependencies in agile software development projects have not previously been a research focus. Drawing on three case studies of agile software projects, and the IS literature, this paper develops an initial taxonomy of agile software project dependencies. Three distinct categories of dependency are found: task, resource, and knowledge dependencies. This paper contributes to theory by providing a taxonomy of dependency types occurring in the area of agile software development. Practitioners can use this taxonomy as sensitising device to ensure they consider dependencies they might face that could hinder their projects, enabling them to take appropriate and timely mitigating action.

Global software development : measuring, approximating and reducing the complexity of global software development using extended axiomatic design theory

This paper considers GSD projects as designed artefacts, and proposes the application of an Extended Axiomatic Design theory to reduce their complexity in order to increase the probability of project success. Using an upper bound estimation of the Kolmogorov complexity of the so-called ‘design matrix’ (as a proxy of Information Content as a complexity measure) we demonstrate on two hypothetical examples how good and bad designs of GSD planning compare in terms of complexity. We also demonstrate how to measure and calculate the ‘structural’ complexity of GSD projects and show that by satisfying all design axioms this ‘structural’ complexity could be minimised.

Challenges relating to RFID implementation within the electronic supply chain management - a practical approach

The use of RHFID (Radio Frequency ldentification) technology can be employed for not only reducing companies management costs but also to track uniquely each shipping container, pallet, case, and product being manufactured, shipped and sold, to increase visibility and accountability in the supply chain. RFID technology connects the supply chain players (i.e., suppliers, manifacturers, distributors, retailers and customers) and allows them to exchange data and product information. Despite these potential benefits, there are challenges and obstacles with the deployment of a RFID-enabled system in the global supply chain. The paper outlines the major RFID issues faced by supply chain management. In this paper, we also present a case study on pharmaceutical supply chain management (SCM) applications by addressing and examining the issues of RFID implementation in a SCM system.

Phenomenological inquiry into the experience of web project managers

The advent of the Internet and the World Wide Web has been instrumental in bringing about the growth in the implementation of web-based information systems (WBIS). Such systems are designed with the aim of improving productivity, data accuracy, and the reduction of paperwork and administrative overheads. Moreover, unlike their conventional non-web-based predecessors, the WBIS are commonly aimed at users who are casual and untrained, geographically distributed and non-homogenous. The dissemination of WBIS necessitates additional infrastructure support in the form of a security system, workflow and transaction management, and web administration. WBIS are commonly developed using an evolutionary approach, whereby the version of the application, acquired from the vendor, is first deployed as a pilot, in order to gather feedback from the target users before the evolutionary cycles commence. While a number of web development methodologies have been proposed by existing research, there is a dearth of empirical evidence that elucidates the experiences of project initiators in pursuing the evolution of web services, a process that undoubtedly involves dealing with stakeholder issues. This research project presents a phenomenological investigation of the experiences of project managers with the implementation of web-based employee service systems (ESS), a domain that has witnessed a sharp growth in Australia in recent times. However, the project managers’ rich, multidimensional account of their experiences with the implementation of ESS revealed the social obstacles and fragility of intra-organizational relationships that demanded a cautious and tactful approach. Thus, the study provides a socio-organizational perspective to web projects in contrast to the functionalist paradigm of current web development methodologies. The research also confirms that consideration of the concerns of stakeholders by project managers is crucial to the successive cycles of ESS evolution. Project managers address stakeholder concerns by pursuing actions that are aimed at encouraging ESS usage, but at the same time, such actions can have consequences necessitating subsequent iterations of system enhancement and improvement. Finally, the research also discovered that despite the different socio-political climate prevalent in various organizations, in which ESS are being implemented, the experiences of project managers in dealing with stakeholder concerns can be captured and independently confirmed in terms of their perceived relevance and usefulness in problem-solving within the application domain.

Incorporating design explanation within formal object-oriented method (FOOM)

Requirements engineering is a commencing phase in the development of either software applications or information systems. It is concerned with understanding and specifying the customer's requirements of the system to be delivered. Throughout the literature, this is agreed to be one of the most crucial and, unfortunately, problematic phases in development. Despite the diversity of research directions, approaches and methods, the question of process understanding and management is still limited. Among contemporary approaches to the improvement of the current practice of Requirements Engineering, Formal Object-Oriented Method (FOOM) has been introduced as a new promising solution. The FOOM approach to requirements engineering is based on a synthesis of socio-organisational theory, the object-oriented approach, and mathematical formal specification. The entire FOOM specification process is evolutionary and involves a large volume of changes in requirements. During this process, requirements evolve through various forms of informal, semi-formal, and formal while maintaining a semantic link between these forms and, most importantly, conforming to the customer's requirements. A deep understanding of the complexity of the requirements model and its dynamics is critical in improving requirements engineering process management. This thesis investigates the benefits of documenting both the evolution of the requirements model and the rationale for that evolution. Design explanation explains and justifies the deliberations of, and decisions made during, the design activity. In this thesis, design explanation is used to describe the requirements engineering process in order to improve understandability of, and traceability within, the evolving requirements specification. The design explanation recorded during this research project is also useful in assisting the researcher in gaining insights into the creativity and opportunistic characteristics of the requirements engineering process. This thesis offers an interpretive investigation into incorporating design explanation within FOOM in order to extend and advantage the method. The researcher's interpretation and analysis of collected data highlight an insight-driven and opportunistic process rather than a strictly and systematically predefined one. In fact, the process was not smoothly evolutionary, but involved occasional 'crisis' points at which the model was reconceptualised, simplified and restructured. Therefore, contributions of the thesis lie not only in an effective incorporation of design explanation within FOOM, but also a deep understanding of the dynamic process of requirements engineering. The new understanding of the complexity of the requirements model and its dynamics suggests new directions for future research and forms a basis for a new approach to process management.

Knowledge mediation in software quality engineering

The risk of failure of the software development process remains high despite many attempts to improve the quality of software engineering. Contemporary approaches to process assurance, such as the capability maturity model have not prevented systemic failures, nor have project management methodologies provided guarantees of software quality. The paper proposes an approach to software quality assurance based on a knowledge mediated concurrent audit, which incorporates essential feedback processes. Through a tightly integrated approach to quality audit, programmers would be empowered to use any chosen methodology to advantage, supported by intelligent monitoring of the essential interactions which occur in the development process. An experimental application implementing some aspects of the proposal is described

Technologies and considerations for developing internet and multiplayer computer games: a tutorial (extended abstract)

Games are universal and probably as old as humankind. Today the development of computer technology, especially the development of fast networks and the Internet, brings games a faster growth than ever before. Game design and development is now a fast-growing entertainment field, with a lot to offer professionally and creatively. In fact, from IT professional’s point of view, creating computer games provides us with all the usual technical challenges associated with software development, such as requirement analysis, architectural design, rapid prototyping, HCI, parallel and distributed processing, code reuse, programming, performance evaluation, testing and maintenance. It also provides challenges on other exciting aspects, such as storyboarding, screenplays, illustration, animation, sound effects, music, and social impact. By developing a computer game from start to finish, one would be able to acquire multi-disciplinary knowledge to become an IT professional for the modern era.